No news is bad news, and this bug prevents the fix for many other bugs. What can be done, @benselme?

@jrfern I don't understand your comment fully.
@benselme can you rebase the PR onto current master, correct the reference to point to bug #106 (as it was a duplicate, please use full URL, avoid relying on users viewing the commit message via GitHub), add an explanation so the commit message is valid on its own (it should be, the issue link should provide more information about the issue while the commit message itself should provide enough information to explain the change (not the fix) to the code and justify it.) Take a look at http://coala.readthedocs.org/en/latest/Getting_Involved/Writing_Good_Commits/ for a summary of common commit message guidelines.

@benselme still around? I can understand frustration of your PR being ignored for such a long time. We took over maintenance shortly ago because the old maintainer (obviously) didn't have enough time to maintain this repo properly. I can assure you, that we will work together with you to get this merged.

@jrfern you seem to be interested in this issue, if @benselme is not around anymore, would you like to ramp this one up to our current standards and submit a replacement PR? We currently don't have the manpower to do more than triaging issues and reviewing and merging PRs because they stacked up pretty high.

I just came back from a long trip. I'll try to fix that PR this week.

@benselme cool, many thanks!

Hasn't this been fixed in 9f099d3 already ?

@benselme fixed indeed. Closing.